| Author |
Thread Statistics | Show CCP posts - 10 post(s) |
|
CCP Prism X
Gallente
C C P
C C P Alliance
   |
Posted - 2010.09.22 15:31:00 -
[1]
 Originally by: EliteSlave
swiftsniping this, I actually look forward to these API changes :D
I have received reports that this is not a proper swiftsnipe!
~ Prism X
EvE Database Developer
Relocating your character to a cozy, secure container since 2006.
Relocating your cozy, secure container to the EVE cemetery since 2008. |
|
|
CCP Prism X
Gallente
C C P
C C P Alliance
|
Posted - 2010.09.22 17:06:00 -
[2]
Originally by: Hiro Logos
Every time you waste a GUID, God kills a kitten. Also, GUIDs don't index well in databases.
For the sake of the discussion:
One can make a case for using GUIDs, a very low fill factor and good maintenance processes and thus avoiding page splits like there's no tomorrow at the cost of ridiculous wastes of space. If that's something that your application usage pattern would gain from doing I wouldn't say you shouldn't do it because it uses GUIDs.
Your statement is however completely right. This and many other factors contribute to us avoiding them like the plague. I just wanted to (post more) mention that there is never any silver bullet in this world. There's always a case for the usage of tools or else they wouldn't exist. 
~ Prism X
EvE Database Developer
Relocating your character to a cozy, secure container since 2006.
Relocating your cozy, secure container to the EVE cemetery since 2008. |
|
|
CCP Prism X
Gallente
C C P
C C P Alliance
|
Posted - 2010.09.22 17:31:00 -
[3]
Edited by: CCP Prism X on 22/09/2010 17:34:41
Edited by: CCP Prism X on 22/09/2010 17:32:38
DUST 514 was only mentioned to explain why we are doing this. I am absolutely not working on DUST 514 and will not comment a single bit on that as it would all be conjecture or, at the least, subject to change. I will however state that I was only referring to the player characters of DUST 514 not any new character types in EVE.
I would like to ask you to please stick to discussions regarding the API. I really cannot comment on the work of my co-workers or imply what it is they are doing. It wouldn't be proper of me.
I can be improper in all sorts of other ways but I do not promise work into the hands of others. I hope you understand.
Edit: Removing a redundant "However". By golly do I like that word!
~ Prism X
EvE Database Developer
Relocating your character to a cozy, secure container since 2006.
Relocating your cozy, secure container to the EVE cemetery since 2008. |
|
|
CCP Prism X
Gallente
C C P
C C P Alliance
|
Posted - 2010.09.23 12:49:00 -
[4]
Originally by: Mono Loco
Correct me if I am wrong, but as long as you (CCP) don't use IDs above the Int32-space applications won't break (?). So lifting all applications to tyrannis 1.2+ static exports and code changes may be delayed without breaking functionality until you (again CCP) run out of Int32-space for itemz?
As I said in the blog it's application specific. I cannot really comment on code I do not know.
For example if you're working in a strongly typed language and your code is fetching an Int16 from a rowset and that ordinal is actually an Int32 in the SDE you will get errors regardless of the actual value.
On the API side all values are returned as XML elements. If the application is working with them all as strings and never casts them to anything you'll get no conversion exceptions. If you cast a value from a string to an x-bit type everything will be alright as long as the numeric representation of the string fits into those x-bits but as soon as it does not you'll get a conversion exception.
And that's the reason for this blog and why it is dedicated to this change alone. It's not up to us whether anything breaks or not. All we can do is give you timely heads-up.
~ Prism X
EvE Database Developer
Relocating your character to a cozy, secure container since 2006.
Relocating your cozy, secure container to the EVE cemetery since 2008. |
|
|
CCP Prism X
Gallente
C C P
C C P Alliance
|
Posted - 2010.09.28 11:56:00 -
[5]
Edited by: CCP Prism X on 28/09/2010 11:56:46
Originally by: Verite Rendition
Edited by: Verite Rendition on 28/09/2010 06:39:35
Thanks for the heads up.
Just to be clear, when you say that locations are considered item IDs, does that include SolarSystemIDs as used by MapSolarSystems and the like? Basically I need to know whether future solar systems, constellations, and regions (if you do a Black Rise again) are going to be 32bit INTs, or if I need to tweak the influence map to use and store 64bit INTs there.
In the SDE's mapSolarSystem the locationIDs will remain as 32-bit integers as mentioned in the Dev Blog. We will also ensure the data in that specific table will remain 32-bit. But as soon as the table has to accommodate shipIDs as locationIDs it will obviously return them as 64-bit, even though I just promised you that systemIDs will never exceed the 32-bit range, as other rows have to support 64 bit ints.
Makes sense?
Edit: For proper closing of bold tag.
~ Prism X
EvE Database Developer
Relocating your character to a cozy, secure container since 2006.
Relocating your cozy, secure container to the EVE cemetery since 2008. |
|
| |
|